What Engineers Know and How They Know It

What Engineers Know and How They Know It  

Cover of 1 ed edition, paperback
Author(s) Walter G. Vincenti
Country United States
Language English, Turkish
Subject(s) History of technology, Aeronautical history
Publisher Johns Hopkins University Press
Publication date 1990
Media type Paperback
Pages 326
ISBN 0-8018-3974-2 (a1k. paper) 0-8018-4588-2 (pbk.)

What Engineers Know and How they Know It: Analytical Studies from Aeronautical History (The Johns Hopkins University Press, 1990) (ISBN:0-8018-4588-2) is a historical reflection on engineering practice in US aeronautics from 1908-1953 written by an accomplished practitioner and instructor. This period represents the dawn of aviation which was fraught with uncertainties and numerous paths to many possible worlds. The book captures two main conclusions from this period. The first order conclusion of this book is about "what engineers know." Five case studies from the history of aeronautical engineering are used to argue engineering often demands its own scientific discoveries. Thus, engineering should be understood as a knowledge-generating activity that includes applied science but is not limited to applied science. The second order conclusion of this book pertains to "how engineers know" by using the same case studies to reveal patterns in the nature of all engineering. These patterns form an “epistemology” of engineering that may point the way to an “engineering method” as something distinct from scientific method.[1] Walter Vincenti ends the work with a general "variation-selection model" for understanding the direction of technological innovation in human history. The book is filled with numerous additional observations and stories told by a practitioner and instructor. This may be why Dr. Michael A. Jackson, author of Structured Design and Problem Frames, once concluded a keynote address to engineers with the statement, "Read Vincenti's book. Read it carefully. Read it one hundred times."[2]

Contents

Author

Walter G. Vincenti (commonly pronounced "vin-sen-tee" in the US or "vin-chen-tee" in Italian) (1917-present) is a Professor Emeritus of Aeronautical and Aerospace Engineering at Stanford University.[3] In 1987 he was inducted into the National Academy of Engineering, “for pioneering contributions to supersonic aircraft aerodynamics and to fundamental understanding of the physical gas dynamics of hypersonic flow.”[4] His important textbook from the first part of his career is, Introduction to Physical Gas Dynamics (1ed ed 1965, 2nd ed 1975).[5] Vincenti in effect had two whole careers: one as a cutting-edge aeronautical engineer and another as a leading historian of technology. This gave him a dual vantage point to think about how technological innovation works. Further, he broadened the relevance of engineering to society by co-founding a Stanford discipline called Values, Technology and Society in 1971—now called Science, Technology and Society.[6] At the age of 90 he published his most recent work with William M. Newman, "On an Engineering Use of Engineering History" which appears in Technology and Culture.[7]

Background

What Engineers Know was first published in 1990 when Mr. Vincenti was 73 years old after full careers in aerospace engineering, the history of technology, and instructing. The five case studies used for evidence in this book come from the first half of the 20th century, 1908-1953. During this period the author worked at the National Advisory Committee for Aeronautics (NACA) from 1940-1957.[8] Four of the five case studies used as evidence in this book were first published independently in Technology and Culture between 1979-1986.[9] During this era, other authors were beginning to refute the view of engineering as only applied science.[10] Then in 1990, Vincenti's five case studies indirectly supported this newer discourse about engineering as a knowledge-generating discipline.

Scope

The profession of "engineering" encompasses a wide scope of practice. Thus, the author narrows the scope of his five case studies in three ways.[11] First, viewed end-to-end, the engineering process contains three phases including design, construction/production and operation. These cases come largely from the design phase of engineering. One exception is the fifth case study on flush-riveted joints which involved an intimate interplay between design and production. Second, design can be categorized as normal or radical. These case studies pertain to normal design. Third, normal design itself is multi-leveled. These levels proceed from project definition down to overall design, major component design, subdivision of component design, and highly specific problems (like planform, airfoil and high-lift devices). These five case studies come mostly from these lower levels. Thus when combined, the scope of these case studies is design, normal design and highly specific problems at the lowest level, "to help redress the neglect of this large and essential area."[12]

Case Study Summary

The five case studies are organized by chapter. Chapter 2 regards airfoil design generally. The early work of Davis illustrates how useful engineering has been done by people who have no formal training in engineering. The Davis wing was instrumental even though Davis did not have the theoretical basis to know how or why. Chapter 3 is about how engineers design in accord with flying qualities satisfactory to pilots. This case study illustrates there can be a key relationship between human behavior and engineering requirements that can greatly affect the outcomes. As such, "artifactual design is a social activity."[13] Chapter 4 instructs the importance of control-volume analysis situations in mechanical design. Control volume analysis was missing in physics textbooks at the time. Thus, engineers had a scientific requirement that was not addressed adequately by any natural science. Importantly, such case studies are examples of why there is such a thing as "engineering science". Chapter 5 regards the dynamic problem of propeller design and selection. The propeller case study illustrates how engineers develop methods to account for the absence of required scientific theory. In this case "parameter variation" was used to map-out and survey a subject where no comprehensive scientific theory (in physics) existed.[14] Finally, chapter 6 describes the problem of designing flush-riveted joints for aircraft. This case study conveys how requirements of production can have a reverse influence on design thus driving iterations between production and design. This case study also illustrates how there are aspects of engineering that cannot adequately be described as science such as the "feel" rivet mechanics developed for how much pressure to apply when completing the aircraft's aluminum stressed-skin structure (see "tacit knowledge" discussion below).

An Epistemology of Engineering (How Engineers Know)

Throughout the book, Walter Vincenti makes epistemology observations pertaining to engineering. The following are six of several observations made throughout the book.[15] These observations do not constitute an "engineering method" per se but he offers a conjecture that they may point the way for further research.[16] He wrote, "in the final paragraph of chapter 5, I also raised the question of whether it might be profitable to look for "engineering method" analogous to but distinguishable from scientific method that has been a fruitful concern for the history of science. Could it be that the variation-selection process outlined here is that method, with its distinctive features lying in the criterion of selection and the vicarious methods used to shortcut direct trial?"[17]

Seven Interactive Elements of Engineering Learning

First, there is a pattern to the iterative engineering discovery process seen in the development of flying-quality specifications.[18] This process is referred to as "Seven Interactive Elements of Engineering Learning" and includes:

  1. Familiarization with vehicle and recognition of problem.
  2. Identification of basic variables and derivation of analytical concepts and criteria.
  3. Development of instruments/piloting techniques for in-flight measurements.
  4. Growth and refinement of pilot opinion regarding desirable flying qualities.
  5. Combine results from 2-4 into a deliberate scheme for flying-quality research.
  6. Measurement of relevant flight characteristics for a cross section of aircraft.
  7. Assessment of results and data on flight characteristics in light of pilot opinion to arrive at general specifications.

The boldface from the original text isolates the steps in a subject-neutral manner.

Six Categories of Engineering Knowledge

Second, there is a pattern in the very categories of knowledge in engineering.[19] These six categories of engineering knowledge are:

  1. Fundamental design concepts
  2. Criteria and specifications
  3. Theoretical tools
  4. Quantitative data
  5. Practical considerations
  6. Design instrumentalities

Seven Knowledge-Generating Activities

Third, Walter Vincenti sees a pattern in knowledge/science generating activities of engineering.[20] These seven Knowledge-Generating Activities include:

  1. Transfer from science
  2. Invention
  3. Theoretical engineering research
  4. Experimental engineering research
  5. Design practice
  6. Production
  7. Direct Trial

Relationship Between Categories and Activities

Fourth, by placing six categories of knowledge and the seven knowledge-generating activities on an x-y table, these knowledge generating activities cut across the categories of knowledge in a partially predictable way. The resulting table serves as an approximation for what engineering tasks may be likely to produce new engineering knowledge.[21] The resulting diagram "is intended for discussion more than a set of hard and fast divisions."[22]

Engineering Knowledge Classification

Fifth, he re-classifies engineering knowledge itself. Knowledge generated by engineering may normally be categorized by phases such as design, production or operations.[23] Another way to think about engineering knowledge categories is descriptive knowledge, prescriptive knowledge and tacit knowledge.[24] He adds Gilbert Ryle's terms "knowing that" and "knowing how"[25] to illustrate the aim of each knowledge category.[26] "Knowing what or that" to do in engineering is a mixture of descriptive and prescriptive knowledge. "Knowing how" to do it is a mixture of prescriptive and tacit knowledge. Thus, these case studies show the need for all three kinds of knowledge in engineering.

Variation-Selection Model of Technological Innovation

Finally, he posits a variation-selection model for knowledge growth. At all levels of design hierarchy, growth of knowledge acts to increase the complexity and power of the variation-selection process by modifying both the mechanism for variation and expanding the processes of selection vicariously. Variation and selection each add two realistic principles for the advancement of technology: blindness to variation and unsureness of selection.[27] Blindness and unsureness characterize the difficult or arduous nature of technology evolution in the variation-selction model.[28] The author then reviews the five case studies retrospectively to demonstrate how variation-selection and blindness-unsureness were at work in each case.[29] In total, "the cumulative growth of engineering knowledge as the result of individual variation-selection processes acts to change the nature of how those processes are carried out."[30]

See also

References

  1. ^ Vincenti, Walter G. What Engineers Know and How They Know It : Analytical Studies from Aeronautical History, Johns Hopkins Studies in the History of Technology [New. Ser., No. 11]. Baltimore: Johns Hopkins University Press, 1990, 169, 256.
  2. ^ Ian Alexander book review http://i.f.alexander.users.btopenworld.com/reviews/vincenti.htm, accessed 23 Jan 2011, 2300.
  3. ^ http://soe.stanford.edu/research/layout.php?sunetid=sts, accessed 24 Jan 2011, 2043.
  4. ^ http://www.members.nae.edu/nae/naepub.nsf/Members+By+UNID/5B3300986C7CFF4C8625755200622ED3?opendocument, accessed 23 Jan 2011, 2230.
  5. ^ Vincenti, Walter G., and Charles H. Kruger. Introduction to Physical Gas Dynamics. Huntington, N.Y.: Krieger, 1975.
  6. ^ Walter C. Post interview 1997, http://www.americanheritage.com/articles/magazine/it/1997/3/1997_3_20.shtml, accessed 23 Jan 2011, 2240.
  7. ^ Walter Vincenti and William Newman. "On an Engineering Use of Engineering History," Technology and Culture. Volume 48, Number 1, January 2007, pp. 245-247.
  8. ^ http://www.americanheritage.com/articles/magazine/it/1997/3/1997_3_20.shtml, accessed 23 Jan 2011, 2245.
  9. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 10.
  10. ^ Bijker, Wiebe E., Thomas Parke Hughes, and T. J. Pinch. The Social Construction of Technological Systems : New Directions in the Sociology and History of Technology. Cambridge, Mass.: MIT Press, 1987. pg 69.
  11. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 6-9.
  12. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 9.
  13. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 11, 237.
  14. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 160-161.
  15. ^ Note: there are many other epistemological observations made throughout the book including a high density of them in Chapter 7.
  16. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 160-161.
  17. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 256.
  18. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 102.
  19. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 208.
  20. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 229.
  21. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 235, Table 7-1.
  22. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 225.
  23. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 195.
  24. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 198.
  25. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 13.
  26. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 198.
  27. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 249.
  28. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 248-249.
  29. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 250-252.
  30. ^ Vincenti, Walter G. What Engineers Know and How They Know It, pg 245.